About the Testing tab

You are here: Programming guide > COM SDK fundamentals > Creating a user interface extension > About the interface extension designer > About the Testing tab

About the Testing tab

The Testing tab of an interface extension designer helps you to test the interface extension you have created.

Refer to the table below for descriptions of each of the options on this tab.

Testing options
Option	Description
Selected vault	Displays the vault on which the buttons on the tab will operate. Click the Clear button to disassociate the interface extension from the vault.
Select the vault used to test your Extension	Click this button to select a vault in which to test the extension.
Compile the project	Click this button to compile the project. This is the same action as running the Make command on the File menu in Visual Basic except that if compilation fails, it will not set the focus to the line that contains the error. Note You cannot compile a new project until it has been saved.
Register Extension	Click this button to register the extension in the selected vault after the interface extension has been compiled. This is the same action as running the Register Extension command in the Configurator.
Automatically register extension before starting debug mode	Enable this option to automatically register the interface extension each time the project is run for debugging. This option is not recommended. There is seldom a need to register an extension more than once.
Start Meridian Enterprise Configurator	Click this button to open the Meridian Enterprise Configurator to perform other configuration operations.
Start Meridian Enterprise PowerUser	Click this button to open the Meridian Enterprise PowerUser client to test the extension.
Extension properties	Click this button to display the properties of the current interface extension in the Properties pane of the Visual Basic IDE.

When it compiles the project, Visual Basic automatically registers the interface extension with Windows as a COM component. This not related to registering an interface extension in a vault.

You should register the interface extension:

Once to make it available in the vault.
After adding properties to the property set definition.
After changing the property set definition. In this case it is even better to create a new test vault.
In a production environment when installing a new release of your interface extension.

After an interface extension is registered in a vault, you need to configure which objects will use the extension. This can be done in the Meridian Enterprise Configurator in one of two ways:

To assign an interface extension to a specific document type, you can add it to the list on the Extensions tab of the document type. When you then select the extension in the Configurator, you will see the document type in the list on the Applies To tab of the extension.
Add the objects to which the interface extension should apply to the list on the Applies To tab.

Tip Press and hold the Ctrl key while clicking the Extension Properties button to launch the Class Editor as shown in the figure below. This dialog gives a detailed view of all classes in the vault and the interface extensions and property sets that apply to it.

Related information

Debugging an interface extension

Registering an interface extension